BSoD:  ATTEMPTED_WRITE_TO_READONLY_MEMORY
ATTEMPTED_WRITE_TO_READONLY_MEMORY With Stopcode: 0x000000BE (0x81D1BE4C , 0x15663121 , 0x88B093F4 , 0x0000000B)Turned on verifier.exe rebooted, gave me a 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATIONTelling me that there's a corrupt driver on the kernel stack that should be replaced.I downloaded Debugging Tools for windows, where do I go from here?
February 25th, 2009 8:03pm

Your action center will give you the driver name. Control Panel, Action Center. MaintenanceRating posts helps other users Mark L. Ferguson MS-MVP
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2009 10:49pm

It only says that no action is needed... And I got another blue screen with SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION with stop code 0xC1And another one while in safe mode with stop code 0x7EStill leaves me a 1001 possibilities which driver is flawed.
February 26th, 2009 12:48am

What makes you so sure it is not a memory problem?Test your memory thoroughly.
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2009 1:27am

bnborg said: What makes you so sure it is not a memory problem?Test your memory thoroughly.Fair point, I'll do another one right away.
February 26th, 2009 1:41am

Did memory checks under various configurations, all the sticks, busses and banks are good. It really is a driver issue, I'm suspecting the kaspersky network driver but can't be too sure, that's why I ask.Blue screen again, this time: PFN_List_Corrupt with stop error 0x1 and 0x4E, just shoot me...
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2009 4:10am

This error indicates thatDriver Vefier found the driver:0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATIONPost back with the text of the dump file analysis (being sure to use the !analyze -v link) in order to help us identify what the driver is.- John
February 26th, 2009 4:34pm

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)A device driver attempting to corrupt the system has been caught. This isbecause the driver was specified in the registry as being suspect (by theadministrator) and the kernel has enabled substantial checking of this driver.If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA willbe among the most commonly seen crashes.Arguments:Arg1: 0000003c, ObReferenceObjectByHandle is being called with a bad handle.Arg2: 8000042c, bad handle passed in,Arg3: 8417d588, object type,Arg4: 00000000, 0.Debugging Details:------------------*** ERROR: Module load completed but symbols could not be loaded for klif.sys*** ERROR: Module load completed but symbols could not be loaded for kl1.sys***** Kernel symbols are WRONG. Please fix symbols to do analysisKaspersky, my suspicion was right, I'll boot it out and recheck.--Edit: It was Kaspersky, all drivers are now verified ok and loaded, or unloaded, or never loaded. Shall I open a new thread about the system just freezing or do it here?
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2009 1:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics